tutorial_qrack.py #1137
tutorial_qrack.py #1137
Conversation
|
@WrathfulSpatula due to how our website is set up, all tutorials are actually executed to generate the site :) So at the moment, your tutorial is failing due to We have two options:
|
|
Thanks a lot for creating this pull request, @WrathfulSpatula ! Josh has added a useful comment above mine, but I will also add the minutiae: if you could look at the bullet points on contributing here, that would be great. But please let me know if something doesn't work right for you and we'll figure it out. Thank you! |
There was a problem hiding this comment.
Thanks @WrathfulSpatula, have left some additional suggestions!
Co-authored-by: Josh Izaac <[email protected]>
Co-authored-by: Josh Izaac <[email protected]>
Co-authored-by: Josh Izaac <[email protected]>
Co-authored-by: Josh Izaac <[email protected]>
|
Hey @WrathfulSpatula, there seems to be an issue installing I tried to |
|
@josh146 This is the exact issue: scikit-build/scikit-build#262 Since The solution for now is simply to add |
|
@josh146 Now it installs, but it's saying that |
This reverts commit de06bd9.
|
If I locally uninstall Then, when I reinstall My guess is that something in the workflow configuration is removing the |
|
Congrats @WrathfulSpatula and thanks @josh146 @ikurecic and @cosenal. Let us know if there is anything that we can do wrt to the tests failing. |
**Title:** The Qrack device back end (with Catalyst) **Summary:** In this tutorial you will learn how to use the Qrack device back end for PennyLane and Catalyst, and you'll learn certain suggested cases of use where Qrack might particularly excel at delivering lightning-fast performance or minimizing required memory resources. (See #1137: this recreates the PR for further review) **Relevant references:** https://github.com/unitaryfund/qrack https://github.com/unitaryfund/pyqrack https://arxiv.org/abs/2304.14969 **Possible Drawbacks:** Not all users might have Catalyst installed, and this tutorial will require Catalyst v0.7 or later. ---- If you are writing a demonstration, please answer these questions to facilitate the marketing process. * GOALS — Why are we working on this now? The Catalyst and Unitary Fund teams are working together to update the Qrack PennyLane device back end (based on open-source code reuse from the Qulacs device and original work with Qrack and Catalyst) to make use of the Catalyst compiler and potentially achieve leading performance on a wide range of `qml.qnode` subroutine qubit widths and applications. Notably, Qrack automatically switches between CPU-based and GPU-used based simulation methods as appropriate to maximize overall performance, whether circuits are wide enough to benefit from thousands of parallel work items in a job dispatched to a GPU. The Qrack device back end is also open source and can serve as an example or basis for other simulator device back ends that may reuse its code. * AUDIENCE — Who is this for? The potential audience includes researchers, educators, students, hobbyists, and anyone with an interest in faster and more efficient quantum computer simulation in PennyLane. * KEYWORDS — What words should be included in the marketing post? GPU, high-performance computing (HPC), hybrid CPU/GPU, near-Clifford simulation, quantum binary decision diagrams (QBDD), vendor-agnostic GPU support (OpenCL), optional CUDA * Which of the following types of documentation is most similar to your file? (more details [here](https://www.notion.so/xanaduai/Different-kinds-of-documentation-69200645fe59442991c71f9e7d8a77f8)) - [ ] Tutorial - [x] Demo - [ ] How-to --------- Co-authored-by: Josh Izaac <[email protected]> Co-authored-by: Ivana Kurečić <[email protected]> Co-authored-by: Ivana Kurečić <[email protected]>
Title:
The Qrack device back end (with Catalyst)
Summary:
In this tutorial you will learn how to use the Qrack device back end for PennyLane and Catalyst, and you'll learn certain suggested cases of use where Qrack might particularly excel at delivering lightning-fast performance or minimizing required memory resources.
Relevant references:
https://github.com/unitaryfund/qrack
https://github.com/unitaryfund/pyqrack
https://arxiv.org/abs/2304.14969
Possible Drawbacks:
Not all users might have Catalyst installed, and this tutorial will require Catalyst v0.7 or later.
If you are writing a demonstration, please answer these questions to facilitate the marketing process.
GOALS — Why are we working on this now?
The Catalyst and Unitary Fund teams are working together to update the Qrack PennyLane device back end (based on open-source code reuse from the Qulacs device and original work with Qrack and Catalyst) to make use of the Catalyst compiler and potentially achieve leading performance on a wide range of
qml.qnodesubroutine qubit widths and applications. Notably, Qrack automatically switches between CPU-based and GPU-used based simulation methods as appropriate to maximize overall performance, whether circuits are wide enough to benefit from thousands of parallel work items in a job dispatched to a GPU. The Qrack device back end is also open source and can serve as an example or basis for other simulator device back ends that may reuse its code.AUDIENCE — Who is this for?
The potential audience includes researchers, educators, students, hobbyists, and anyone with an interest in faster and more efficient quantum computer simulation in PennyLane.
KEYWORDS — What words should be included in the marketing post?
GPU, high-performance computing (HPC), hybrid CPU/GPU, near-Clifford simulation, quantum binary decision diagrams (QBDD), vendor-agnostic GPU support (OpenCL), optional CUDA
Which of the following types of documentation is most similar to your file?
(more details here)